This step is used to change the assignment of an account or remove all assignments from an account. The account can be assigned to any Internal or Third Party queue. This step runs automatically and is not presented to users executing the workflow. This step also forces the account in the queue and overrides the queuing logic.

Queue logic is ignored until the account is removed by the assignment workflow step.

This step runs automatically and is not presented to users executing the workflow. This workflow step is used to present a user with a Yes or No decision. Depending on the answer chosen, users are branched out into a specific path in a workflow. This step can be made automated where system administrators assign business rules to automatically guide a user down a Yes or No path. 

With the automated decision step, administrators may also configure the step to include an Undetermined decision. When this decision type is configured, users may be required to manually complete the workflow.

This step is used to distribute accounts over multiple queues. This uses the same concept as the Assignment workflow step to force accounts in the queues and override all queuing logic.

The Distribution Workflow step distributes accounts evenly across multiple queues. If there are an odd number of accounts satisfying the condition of an Automated workflow including the Distribution Workflow Step, then the accounts are distributed as evenly as possible over the assigned queues. For example, if 131 accounts satisfy the condition of the Automated workflow and three queues are assigned to the Distribution Step, then the accounts are distributed as follows: 44, 44, 43.

This step runs automatically and is not presented to users executing the workflow. This workflow step is used to execute business rules within a workflow. Workflow rules are configured by system administrators to execute while a workflow is running in order to automatically make a decision based on certain conditions and/or display a message regarding next actions. 

If an error exists within the rule logic, an error message displays upon execution of this workflow step. If an error message is received while executing this workflow step, please contact your system administrator.

This step is used to record a payment on the account in context. If there is a promise on the account, the payment is applied to the promise. This step can be incorporated into a workflow if an institution does not have a payment import. Payments recorded through this step appear on the Payment History screen.

Payments are automatically imported from an institution's core system; therefore, this workflow step is not needed for those payments to appear on the Payment History screen.

This step is a component of the Temenos Lifecycle Management Suite API. Customer-built applications can be integrated directly into workflows within the context of the Lifecycle Management Suite. Thus, these custom built applications can provide integration with the Host or other systems that the Lifecycle Management Suite does not currently integrate with, but also take advantage of the security, process control and auditing capabilities of the Lifecycle Management Suite. Please contact a System Administrator for directions in completing this workflow step.